File Size of Module/Project Archive

Hi

Is there a way to determine what the file size of a module or project archive will be prior to creating the archive? I'm using DOORS 8.3.

Thanks
Peter.Dawson - Mon Jan 11 21:44:39 EST 2010

Re: File Size of Module/Project Archive
Mathias Mamsch - Tue Jan 12 03:55:27 EST 2010

That is highly unlikely, since the archives are zip-compressed. How would you know the size of a compressed file before you actually do the compression? Why do you need the archive size before creating the archive?
Regards, Mathias

Re: File Size of Module/Project Archive
Peter.Dawson - Tue Jan 12 17:57:15 EST 2010

Mathias Mamsch - Tue Jan 12 03:55:27 EST 2010
That is highly unlikely, since the archives are zip-compressed. How would you know the size of a compressed file before you actually do the compression? Why do you need the archive size before creating the archive?
Regards, Mathias

I don't really care so much about the compressed size, I only am concerned with the actual restored size.

I need to move DOORS data from a database on one network, to a database on another secure, isolated network. The archive file is just the transport mechanism and doesn't really matter. I'm more concerned with the size of the project once it is restored on the other database. The amount of disk space allocated to the database on the isolated network is tightly constrained and I need to provide IT with a fairly close estimate of the size increase to the database due to the data transfer as well as requirements for growth.

This would all be easy if I could just go to DOORS explorer like I do Windows explorer, and: right-click -> properties -> check the file size of a module or project.

Re: File Size of Module/Project Archive
SystemAdmin - Tue Jan 12 18:55:32 EST 2010

Peter.Dawson - Tue Jan 12 17:57:15 EST 2010
I don't really care so much about the compressed size, I only am concerned with the actual restored size.

I need to move DOORS data from a database on one network, to a database on another secure, isolated network. The archive file is just the transport mechanism and doesn't really matter. I'm more concerned with the size of the project once it is restored on the other database. The amount of disk space allocated to the database on the isolated network is tightly constrained and I need to provide IT with a fairly close estimate of the size increase to the database due to the data transfer as well as requirements for growth.

This would all be easy if I could just go to DOORS explorer like I do Windows explorer, and: right-click -> properties -> check the file size of a module or project.

Hi Peter,

you can exactly do as you described -

option a)
if you get the unique id for the project of interest you can navigate to your data drive (on the server) and right click properties will give you a rough indication of the size for the project.

option b)
go and have a look on smartdxl.com - there is exactly the script as you wanted it. - its located under a heading "Size of Project on Disc"

hope this helps
werner